Add regression tests for multi-tenant durability agents (GH-2085)#2148
Merged
jeremydmiller merged 2 commits intomainfrom Feb 9, 2026
Merged
Add regression tests for multi-tenant durability agents (GH-2085)#2148jeremydmiller merged 2 commits intomainfrom
jeremydmiller merged 2 commits intomainfrom
Conversation
Verify that scheduled messages and durability agents work correctly for non-master tenant databases in multi-tenant PostgreSQL setups. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
main, confirming the bug reported in Scheduled messages and DLQ replays not processed for non-master tenants in PostgreSQL multi-tenancy #2085 was fixed between v5.12.1 and the current codebaseTests added
all_tenant_durability_agents_are_started— verifies 3 durability agents start (main + 2 tenants)scheduled_message_for_tenant_is_processed— schedules a message for a specific tenant and confirms it is handled with the correct TenantIdscheduled_messages_for_all_tenants_are_processed— schedules messages for both tenants and the main database, confirms all are processed correctlyTest plan
dotnet test --filter "multi_tenant_durability_agents")dotnet test --filter "MultiTenancy")Closes GH-2085
🤖 Generated with Claude Code -- with clean up by @jeremydmiller too!